Multiple-application mobile device methods, systems, and computer program products

ABSTRACT

Methods, computer software, apparatuses, and systems are described in connection with a mobile device including at least one processor operatively coupled to a touchscreen and memory. The memory stores a first application and a second application. The mobile device is configured for: presenting, utilizing the touchscreen, at least one menu including a plurality of interface elements including a first application interface element associated with the first application and a second application interface element associated with the second application; detecting, utilizing the touchscreen, a first user input in connection with the first application interface element associated with the first application; in response to the first user input, presenting, utilizing the touchscreen, a first visual component for presenting first data associated with the first application; detecting, utilizing the touchscreen, a second user input in connection with the second application interface element associated with the second application; in response to the second user input, presenting, utilizing the touchscreen, a second visual component for presenting second data associated with the second application, such that a first border of the first visual component corresponds to a second border of the second visual component; detecting, utilizing the touchscreen, a third user input; and in response to the third user input, automatically changing, utilizing the at least one processor and the touchscreen, the presentation of the first visual component and the second visual component, such that the first border of the first visual component corresponds to the second border of the second visual component.

RELATED APPLICATIONS

The present application is continuation of, and claims priority to U.S. patent application Ser. No. 14/331,096, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR BINDING ATTRIBUTES BETWEEN VISUAL COMPONENTS,” filed Jul. 14, 2014; which, in turn, is a continuation of, and claims priority to U.S. patent application Ser. No. 12/956,008, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR BINDING ATTRIBUTES BETWEEN VISUAL COMPONENTS,” filed Nov. 30, 2010, now issued as U.S. Pat. No. 8,780,130, all of which are incorporated herein by reference in their entirety for all purposes.

BACKGROUND

While some applications can be used alone, some applications are used together. Often there is no integration and/or cooperation between or among applications used at the same time by a user. Even in application suites, cooperation is limited to features that ease data sharing between or among applications in a particular application suite. For example, documents often include both text and media such as images from pictures, graphs, and drawings. Word processors provide rich feature sets for creating and editing text, but provide relatively weak or no features for creating and editing other forms of data. As a result, users work on text for a document in a word processor, images in an image editor, and drawings using a drawing tool such as a computer aided design (CAD) tool. Users spend significant time managing the user interfaces of these various applications in order to access the data desired in the application desired.

Accordingly, there exists a need for methods, systems, and computer program products for binding attributes between visual components.

SUMMARY

The following presents a simplified summary of the disclosure in order to provide a basic understanding to the reader. This summary is not an extensive overview of the disclosure and it does not identify key/critical elements of the invention or delineate the scope of the invention. Its sole purpose is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

Methods, computer software, apparatuses, and systems are described in connection with a mobile device including at least one processor operatively coupled to a touchscreen and memory. The memory stores a first application and a second application. The mobile device is configured for: presenting, utilizing the touchscreen, at least one menu including a plurality of interface elements including a first application interface element associated with the first application and a second application interface element associated with the second application; detecting, utilizing the touchscreen, a first user input in connection with the first application interface element associated with the first application; in response to the first user input, presenting, utilizing the touchscreen, a first visual component for presenting first data associated with the first application; detecting, utilizing the touchscreen, a second user input in connection with the second application interface element associated with the second application; in response to the second user input, presenting, utilizing the touchscreen, a second visual component for presenting second data associated with the second application, such that a first border of the first visual component corresponds to a second border of the second visual component; detecting, utilizing the touchscreen, a third user input; and in response to the third user input, automatically changing, utilizing the at least one processor and the touchscreen, the presentation of the first visual component and the second visual component, such that the first border of the first visual component corresponds to the second border of the second visual component.

BRIEF DESCRIPTION OF THE DRAWINGS

Objects and advantages of the present invention will become apparent to those skilled in the art upon reading this description in conjunction with the accompanying drawings, in which like reference numerals have been used to designate like or analogous elements, and in which:

FIG. 1 is a block diagram illustrating an exemplary hardware device included in and/or otherwise providing an execution environment in which the subject matter may be implemented;

FIG. 2 is a flow diagram illustrating a method for binding attributes between visual components according to an aspect of the subject matter described herein;

FIG. 3 is a block diagram illustrating an arrangement of components for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 4 a is a block diagram illustrating an arrangement of components for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 4 b is a block diagram illustrating an arrangement of components for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 4 c is a block diagram illustrating an arrangement of components for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 4 d is a block diagram illustrating an arrangement of components for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 5 is a network diagram illustrating an exemplary system for binding attributes between visual components according to another aspect of the subject matter described herein;

FIG. 6 a is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein;

FIG. 6 b is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein; and

FIG. 7 is an illustration of binding information according to another aspect of the subject matter described herein.

DETAILED DESCRIPTION

One or more aspects of the disclosure are described with reference to the drawings, wherein like reference numerals are generally utilized to refer to like elements throughout, and wherein the various structures are not necessarily drawn to scale. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects of the disclosure. It may be evident, however, to one skilled in the art, that one or more aspects of the disclosure may be practiced with a lesser degree of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more aspects of the disclosure.

An exemplary device included in an execution environment that may be configured according to the subject matter is illustrated in FIG. 1. An execution environment includes an arrangement of hardware and, optionally, software that may be further configured to include an arrangement of components for performing a method of the subject matter described herein. An execution environment includes and/or is otherwise provided by one or more devices. An execution environment may include a virtual execution environment including software components operating in a host execution environment. Exemplary devices included in or otherwise providing suitable execution environments for configuring according to the subject matter include personal computers, notebook computers, tablet computers, servers, handheld and other mobile devices, multiprocessor devices, distributed devices and/or systems, consumer electronic devices, routers, communication servers, and/or other network-enabled devices. Those skilled in the art will understand that the components illustrated in FIG. 1 are exemplary and may vary by particular execution environment.

FIG. 1 illustrates hardware device 100 included in execution environment 102. FIG. 1 illustrates that execution environment 102 includes instruction-processing unit (IPU) 104, such as one or more microprocessors; physical IPU memory 106 including storage locations identified by addresses in a physical memory address space of IPU 104; persistent secondary storage 108, such as one or more hard drives and/or flash storage media; input device adapter 110, such as a key or keypad hardware, a keyboard adapter, and/or a mouse adapter; output device adapter 112, such as a display and/or an audio adapter for presenting information to a user; a network interface component, illustrated by network interface adapter 114, for communicating via a network such as a LAN and/or WAN; and a communication mechanism that couples elements 104-114, illustrated as bus 116. Elements 104-114 may be operatively coupled by various means. Bus 116 may comprise any type of bus architecture, including a memory bus, a peripheral bus, a local bus, and/or a switching fabric.

IPU 104 is an instruction-execution machine, apparatus, or device. Exemplary IPUs include one or more microprocessors, digital signal processors (DSPs), graphics processing units, application-specific integrated circuits (ASICs), and/or field programmable gate arrays (FPGAs). In the description of the subject matter herein, the terms “IPU” and “processor” are used interchangeably. IPU 104 may access machine code instructions and data via one or more memory address spaces in addition to the physical memory address space. A memory address space includes addresses identifying locations in a processor memory. The addresses in a memory address space are included in defining a processor memory. IPU 104 may have more than one processor memory. Thus, IPU 104 may have more than one memory address space. IPU 104 may access a location in a processor memory by processing an address identifying the location. The processed address may be in an operand of a machine code instruction and/or may be identified in a register or other portion of IPU 104.

FIG. 1 illustrates virtual IPU memory 118 spanning at least part of physical IPU memory 106 and at least part of persistent secondary storage 108. Virtual memory addresses in a memory address space may be mapped to physical memory addresses identifying locations in physical IPU memory 106. An address space for identifying locations in a virtual processor memory is referred to as a virtual memory address space; its addresses are referred to as virtual memory addresses; and its IPU memory is referred to as a virtual IPU memory or virtual memory. The terms “IPU memory” and “processor memory” are used interchangeably herein. Processor memory may refer to physical processor memory, such as IPU memory 106, and/or may refer to virtual processor memory, such as virtual IPU memory 118, depending on the context in which the term is used.

Physical IPU memory 106 may include various types of memory technologies. Exemplary memory technologies include static random access memory (SRAM) and/or dynamic RAM (DRAM) including variants such as dual data rate synchronous DRAM (DDR SDRAM), error correcting code synchronous DRAM (ECC SDRAM), and/or RAMBUS DRAM (RDRAM). Physical IPU memory 106 may include volatile memory as illustrated in the previous sentence and/or may include nonvolatile memory such as nonvolatile flash RAM (NVRAM) and/or ROM.

Persistent secondary storage 108 may include one or more flash memory storage devices, one or more hard disk drives, one or more magnetic disk drives, and/or one or more optical disk drives. Persistent secondary storage may include removable media. The drives and their associated computer-readable storage media provide volatile and/or nonvolatile storage for computer-readable instructions, data structures, program components, and other data for execution environment 102.

Execution environment 102 may include software components stored in persistent secondary storage 108, in remote storage accessible via a network, and/or in a processor memory. FIG. 1 illustrates execution environment 102 including operating system 120, one or more applications 122, and other program code and/or data components illustrated by other libraries and subsystems 124. In an aspect, some or all software components may be stored in locations accessible to IPU 104 in a shared memory address space shared by the software components. The software components accessed via the shared memory address space are stored in a shared processor memory defined by the shared memory address space. In another aspect, a first software component may be stored in one or more locations accessed by IPU 104 in a first address space and a second software component may be stored in one or more locations accessed by IPU 104 in a second address space. The first software component is stored in a first processor memory defined by the first address space and the second software component is stored in a second processor memory defined by the second address space.

Software components typically include instructions executed by IPU 104 in a computing context referred to as a “process”. A process may include one or more “threads”. A “thread” includes a sequence of instructions executed by IPU 104 in a computing sub-context of a process. The terms “thread” and “process” may be used interchangeably herein when a process includes only one thread.

Execution environment 102 may receive user-provided information via one or more input devices illustrated by input device 128. Input device 128 provides input information to other components in execution environment 102 via input device adapter 110. Execution environment 102 may include an input device adapter for a keyboard, a touch screen, a microphone, a joystick, a television receiver, a video camera, a still camera, a document scanner, a fax, a phone, a modem, a network interface adapter, and/or a pointing device, to name a few exemplary input devices.

Input device 128 included in execution environment 102 may be included in device 100 as FIG. 1 illustrates or may be external (not shown) to device 100. Execution environment 102 may include one or more internal and/or external input devices. External input devices may be connected to device 100 via corresponding communication interfaces such as a serial port, a parallel port, and/or a universal serial bus (USB) port. Input device adapter 110 receives input and provides a representation to bus 116 to be received by IPU 104, physical IPU memory 106, and/or other components included in execution environment 102.

Output device 130 in FIG. 1 exemplifies one or more output devices that may be included in and/or may be external to and operatively coupled to device 100. For example, output device 130 is illustrated connected to bus 116 via output device adapter 112. Output device 130 may be a display device. Exemplary display devices include liquid crystal displays (LCDs), light emitting diode (LED) displays, and projectors. Output device 130 presents output of execution environment 102 to one or more users. In some embodiments, an input device may also include an output device. Examples include a phone, a joystick, and/or a touch screen. In addition to various types of display devices, exemplary output devices include printers, speakers, tactile output devices such as motion-producing devices, and other output devices producing sensory information detectable by a user.

A device included in or otherwise providing an execution environment may operate in a networked environment communicating with one or more devices via one or more network interface components. The terms “communication interface component” and “network interface component” are used interchangeably herein. FIG. 1 illustrates network interface adapter (NIA) 114 as a network interface component included in execution environment 102 to operatively couple device 100 to a network. A network interface component includes a network interface hardware (NIH) component and optionally a software component. The terms “network node” and “node” in this document both refer to a device having a network interface component for operatively coupling the device to a network.

Exemplary network interface components include network interface controller components, network interface cards, network interface adapters, and line cards. A node may include one or more network interface components to interoperate with a wired network and/or a wireless network. Exemplary wireless networks include a BLUETOOTH network, a wireless 802.11 network, and/or a wireless telephony network (e.g., a cellular, PCS, CDMA, and/or GSM network). Exemplary network interface components for wired networks include Ethernet adapters, Token-ring adapters, FDDI adapters, asynchronous transfer mode (ATM) adapters, and modems of various types. Exemplary wired and/or wireless networks include various types of LANs, WANs, and/or personal area networks (PANs). Exemplary networks also include intranets and internets such as the Internet.

The terms “device” and “node” as used herein refer to one or more devices and nodes, respectively, providing and/or otherwise included in an execution environment unless clearly indicated otherwise.

The components of a user interface are generically referred to herein as user interface elements. More specifically, visual components of a user interface are referred to herein as visual interface elements. A visual interface element may be a visual component of a graphical user interface (GUI). Exemplary visual interface elements include windows, textboxes, sliders, list boxes, drop-down lists, spinners, various types of menus, toolbars, ribbons, combo boxes, tree views, grid views, navigation tabs, scrollbars, labels, tooltips, text in various fonts, balloons, dialog boxes, and various types of button controls including check boxes and radio buttons. An application interface may include one or more of the elements listed. Those skilled in the art will understand that this list is not exhaustive. The terms “visual representation”, “visual component”, and “visual interface element” are used interchangeably in this document. Other types of user interface elements include audio output components referred to as audio interface elements, tactile output components referred to as tactile interface elements, and the like.

A visual component may be presented in a two-dimensional presentation where a location may be defined in a two-dimensional space having a vertical dimension and a horizontal dimension. A location in a horizontal dimension may be referenced according to an X-axis and a location in a vertical dimension may be referenced according to a Y-axis. In another aspect, a visual component may be presented in a three-dimensional presentation where a location may be defined in a three-dimensional space having a depth dimension in addition to a vertical dimension and a horizontal dimension. A location in a depth dimension may be identified according to a Z-axis. A visual component in a two-dimensional presentation may be presented as if a depth dimension existed, allowing the visual component to overlie and/or underlie some or all of another visual component.

An order of visual components in a depth dimension is herein referred to as a “Z-order”. The term “Z-value” as used herein refers to a location in a Z-order, or an order of visual components along a Z-axis. A Z-order specifies the front-to-back ordering of visual components in a presentation space. A visual component with a higher Z-value than another visual component may be defined as being on top of or closer to the front than the other visual component.

A “user interface (UI) element handler” component, as the term is used in this document, includes a component configured to send information representing a program entity for presenting a user-detectable representation of the program entity by an output device, such as a display. A “program entity” is an object included in and/or otherwise processed by an application or executable program component. The user-detectable representation is presented based on the sent information. The sent information is referred to herein as “presentation information”. Presentation information may include data in one or more formats. Exemplary formats include image formats such as JPEG, video formats such as MP4, markup language data such as HTML and other XML-based markup, and/or instructions such as those defined by various script languages, byte code, and/or machine code. For example, a web page received by a browser from a remote application provider may include hypertext markup language (HTML), ECMAScript, and/or byte code for presenting one or more user interface elements included in a user interface of the remote application. Components configured to send information representing one or more program entities for presenting particular types of output by particular types of output devices include visual interface element handler components, audio interface element handler components, tactile interface element handler components, and the like.

A representation of a program entity may be stored and/or otherwise maintained in a presentation space. As used in this document, the term “presentation space” refers to a storage region allocated and/or otherwise provided for storing presentation information, which may include audio, visual, tactile, and/or other sensory data for presentation by and/or on an output device. For example, a buffer for storing an image and/or text string may be a presentation space. A presentation space may be physically and/or logically contiguous or non-contiguous. A presentation space may have a virtual as well as a physical representation. A presentation space may include a storage location in a processor memory, secondary storage, a memory of an output adapter device, and/or a storage medium of an output device. A screen of a display, for example, includes a presentation space.

As used herein, the term “program” or “executable” refers to any data representation that may be translated into a set of machine code instructions and optionally associated program data. Thus, a program component or executable component may include an application, a shared or non-shared library, and a system command. Program representations other than machine code include object code, byte code, and source code. Object code includes a set of instructions and/or data elements that either are prepared for linking prior to loading or are loaded into an execution environment. When in an execution environment, object code may include references resolved by a linker and/or may include one or more unresolved references. The context in which this term is used will make clear that state of the object code when it is relevant. This definition can include machine code and virtual machine code, such as Java™ byte code.

As used herein, an “addressable entity” is a portion of a program, specifiable in programming language in source code. An addressable entity is addressable in a program component translated from the source code in a compatible execution environment. Examples of addressable entities include variables, constants, functions, subroutines, procedures, modules, methods, classes, objects, code blocks, and labeled instructions. A code block includes one or more instructions in a given scope specified in a programming language. An addressable entity may include a value. In some places in this document “addressable entity” refers to a value of an addressable entity. In these cases, the context will clearly indicate that the value is being referenced.

Addressable entities may be written in and/or translated to a number of different programming languages and/or representation languages, respectively. An addressable entity may be specified in and/or translated into source code, object code, machine code, byte code, and/or any intermediate language(s) for processing by an interpreter, compiler, linker, loader, and/or analogous tool.

The block diagram in FIG. 3 illustrates an exemplary system for binding attributes between visual components according to the method illustrated in FIG. 2. FIG. 3 illustrates a system, adapted for operation in an execution environment, such as execution environment 102 in FIG. 1, for performing the method illustrated in FIG. 2. The system illustrated includes a user interface monitor component 302, a binding director component 304, a binding monitor component 306, and a change director component 308. The execution environment includes an instruction-processing unit, such as IPU 104, for processing an instruction in at least one of the user interface monitor component 302, the binding director component 304, the binding monitor component 306, and the change director component 308. Some or all of the exemplary components illustrated in FIG. 3 may be adapted for performing the method illustrated in FIG. 2 in a number of execution environments. FIGS. 4 a-d include block diagrams illustrating the components of FIG. 3 and/or analogs of the components of FIG. 3 adapted for operation in various execution environments 401 including or otherwise provided by one or more devices and/or nodes.

FIG. 1 illustrates components of an exemplary device that may at least partially provide and/or otherwise be included in an execution environment. The components illustrated in FIGS. 4 a-d may be included in or otherwise combined with the components of FIG. 1 to create a variety of arrangements of components according to the subject matter described herein.

FIG. 5 illustrates user node 502 as an exemplary device that in various aspects may be included in and/or otherwise adapted for providing any of execution environments 401 illustrated in FIGS. 4 a-c each illustrating a different adaptation of the arrangement of components in FIG. 3. As illustrated in FIG. 5, user node 502 is operatively coupled to network 504 via a network interface component, such as network interface adapter 114. Alternatively or additionally, an adaptation of an execution environment 401 may include and/or may otherwise be provided by a device that is not operatively coupled to a network. A server device is illustrated by application provider node 506. Application provider node 506 may be included in and/or otherwise adapted for providing execution environment 401 d illustrated in FIG. 4 d. As illustrated in FIG. 5, application provider node 506 is operatively coupled to network 504 via a network interface component included in execution environment 401 d.

FIG. 4 a illustrates execution environment 401 a hosting application 403 a including an adaptation of the arrangement of components in FIG. 3. FIG. 4 b illustrates execution environment 401 b hosting browser 403 b including an adaptation of the arrangement of components in FIG. 3 that may operate at least partially in a network application agent 405 b received from a remote application provider, such as network application 403 d in FIG. 4 d. Browser 403 b and execution environment 401 b may provide at least part of an execution environment for network application agent 405 b that may be received via a network from a network application operating in a remote execution environment. FIG. 4 c illustrates an arrangement of the components in FIG. 3 adapted to operate in GUI subsystem 437 c of execution environment 401 c. The arrangement in FIG. 4 c may mediate communication between applications 403 c and one or more output devices, such as display 130 in FIG. 1.

FIG. 4 d illustrates execution environment 401 d configured to host one or more network applications, such as a web service, illustrated by network application 403 d. FIG. 4 d also illustrates network application platform 409 d that may provide services to one or more network applications. Network application 403 d includes yet another adaptation of the arrangement of components in FIG. 3.

The various adaptations of the arrangement in FIG. 3 are not exhaustive. For example, those skilled in the art will see based on the description herein that arrangements of components for performing the method illustrated in FIG. 2 may be at least partially included in an application and at least partially external to the application. Further, arrangements for performing the method illustrated in FIG. 2 may be distributed across more than one node and/or execution environment. For example, such an arrangement may operate at least partially in browser 403 b in FIG. 4 b and at least partially in execution environment 401 d in and/or external to network application 403 d in FIG. 4 d.

FIGS. 4 a-d illustrate adaptations of network stacks 411 configured for sending and receiving messages over a network, such as network 504, via a network interface component. Network application platform 409 d in FIG. 4 d provides services to one or more network applications. In various aspects, network application platform 409 d may include and/or interoperate with a web server. FIG. 4 d also illustrates network application platform 409 d configured for interoperating with network stack 411 d. Network stacks 411 may support the same protocol suite, such as TCP/IP, or may communicate via a network gateway or other protocol translation device and/or service. For example, browser 403 b in FIG. 4 b and network application platform 409 d in FIG. 4 d may interoperate via their respective network stacks: network stack 411 b and network stack 411 d.

FIGS. 4 a-d respectively illustrate applications 403 that may communicate via one or more application layer protocols. FIGS. 4 a-d respectively illustrate application protocol components 413 for communicating via one or more application layer protocols. Exemplary application protocols include hypertext transfer protocol (HTTP) and instant messaging and presence (XMPP-IM) protocol. Matching protocols enabling applications 403 to communicate via network 504 in FIG. 5 are not required, if communication is via a protocol gateway or other protocol translator.

In FIG. 4 b, browser 403 b may receive some or all of network application agent 405 b in one or more messages sent from a network application, such as network application 403 d via network application platform 409 d, a network stack 411, a network interface component, and optionally an application protocol component 413. In FIG. 4 b, browser 403 b includes content manager component 415 b. Content manager component 415 b may interoperate with one or more of application protocol components 413 b and/or network stack 411 b to receive the message or messages including some or all of network application agent 405 b.

Network application agent 405 b may include a web page for presenting a user interface for network application 403 d. The web page may include and/or reference data represented in one or more formats including HTML and/or other markup language, ECMAScript or other scripting language, byte code, image data, audio data, and/or machine code.

In an example, in response to a request received from browser 403 b in FIG. 4 b operating in user node 502 in FIG. 5, controller component 417 d, in FIG. 4 d, operating in application provider node 506 may invoke model subsystem 419 d to perform request-specific processing. Model subsystem 419 d may include any number of request handlers (not shown) for dynamically generating data and/or retrieving data from model database 421 d based on the request. Controller component 417 d may further invoke template engine component 423 d to identify one or more templates and/or static data elements for generating a user interface for representing a response to the received request. FIG. 4 d illustrates template database 425 d including exemplary template 427 d. FIG. 4 d illustrates template engine 423 d as a component in view subsystem 429 d configured to return responses to processed requests in a presentation format suitable for a client, such as browser 403 b. View subsystem 429 d may provide the presentation data to controller component 417 d to send to browser 403 b in response to the request received from browser 403 b. Some or all of network application agent 405 b may be sent to browser 403 b via network application platform 409 d as described above.

While the example describes sending some or all of network application agent 405 b in response to a request, network application 403 d additionally or alternatively may send some or all of a network application agent to browser 403 b via one or more asynchronous messages. In an aspect, an asynchronous message may be sent in response to a change detected by network application 403 d. Publish-subscribe protocols, such as the presence protocol specified by XMPP-IM, are exemplary protocols for sending messages asynchronously.

The one or more messages including information representing some or all of network application agent 405 b in FIG. 4 b may be received by content manager component 415 b via one or more of application protocol component(s) 413 b and network stack 411 b as described above. In FIG. 4 b, browser 403 b includes one or more content handler components 431 b to process received data according to its data type, typically identified by a MIME-type identifier. Exemplary content handler components 431 b include a text/html content handler component for processing HTML documents; an application/xmpp-xml content handler component for processing XMPP streams including presence tuples, instant messages, and publish-subscribe data as defined by various XMPP specifications; one or more video content handler components for processing video streams of various types; and still image data content handler components for processing various images types. Content handler components 431 b process received data and may provide a representation of the processed data to one or more user interface (UI) element handler components 433 b.

UI element handler components 433 are illustrated in presentation controller components 435 in FIG. 4 a, FIG. 4 b, and FIG. 4 c. A presentation controller component 435 may manage the visual, audio, and/or other types of output of its including application 403 as well as receive and route detected user and other inputs to components and extensions of its including application 403. With respect to FIG. 4 b, a UI element handler component 433 b in various aspects may be adapted to operate at least partially in a content handler component 431 b such as a text/html content handler component and/or a script content handler component. Additionally or alternatively, a UI element handler component 433 in an execution environment 401 may operate in and/or as an extension of its including application 403. For example, a plug-in may provide a virtual machine, for a UI element handler component received as a script and/or byte code, that may operate as an extension in application 403 and/or external to and interoperating with application 403.

FIGS. 6 a-b respectively illustrate display presentation spaces 602 of a display in and/or operatively coupled to a device. FIGS. 6 a-b illustrate first app visual components 604-1 and second app visual components 604-2 in respective presentation spaces 602. The various app visual components 604 illustrated in FIGS. 6 a-b are described as user interfaces of various applications 403 and other components illustrated in FIGS. 4 a-d as required in describing the subject matter herein. An app visual component 604 may be provided as a user interface of multiple applications interoperating. For example, an app visual component 604 and/or a visual component included in an app visual component 604 may be presented via interoperation of browser 403 b, network application agent 405 b, and network application 403 d illustrated in FIG. 4 b and FIG. 4 d. Browser 403 b may operate in user node 502, and network application 403 d may operate in application provider node 506. Network application agent 405 b may be provided to user node 502 by application provider node 506 via network 504, as described above.

Various UI elements of applications 403 described above may be presented by one or more UI element handler components 433 in FIGS. 4 a-c and/or by one or more template engines 423 d in FIG. 4 d. In an aspect, illustrated in FIGS. 4 a-4 c, UI element handler component(s) 433 of one or more applications 403 is/are configured to send representation information representing a visual interface element, such as operation bar 612-2 a in FIG. 6 a, to a GUI subsystem 437. A GUI subsystem 437 may instruct a corresponding graphics subsystem 439 to draw the visual interface element in a region of display presentation space 602 a, based on presentation information received from a corresponding UI element handler component 433.

Input may be received corresponding to a UI element via an input driver 441 illustrated in FIGS. 4 a-c in various adaptations. For example, a user may move a mouse to move a pointer presented in display presentation space 602 a in FIG. 6 a over an operation user interface element presented in an operation bar 612-2 a. A user may provide an input detected by the mouse. The detected input may be received by a GUI subsystem 437 via an input driver 441 as an operation or command indicator based on the association of the shared location of the pointer and the operation user interface element in display presentation space 602 a.

In FIGS. 6 a-b, first app visual components 604-1 and second app visual components 604-2 are collectively and generically referred to as app visual components(s) 604. App visual components 604 in FIGS. 6 a-b illustrate a number of visual user interface elements commonly found in application user interfaces. Menu bars 606-1 are illustrated in first app visual components 604-1 in FIGS. 6 a-b. Menu bars 606-1 are illustrated including menu controls for receiving user input to identify commands to perform. App visual components 604 also illustrate user interface elements providing respective application presentation spaces 608 for presenting content including other visual components illustrated by resource user interface elements 6141 a through 6142 n in FIG. 6 a representing respective resources.

With reference to FIG. 2, block 202 illustrates that the method includes detecting a first visual component including a first presentation space for presenting first data by an operating first application. Accordingly, a system for binding attributes between visual components includes means for detecting a first visual component including a first presentation space for presenting first data by an operating first application. For example, as illustrated in FIG. 3, user interface monitor component 302 is configured for detecting a first visual component including a first presentation space for presenting first data by an operating first application. FIGS. 4 a-d illustrate user interface monitor components 402 as adaptations and/or analogs of user interface monitor component 302 in FIG. 3. One or more user interface monitor components 402 operate in an execution environment 401.

In FIG. 4 a, user interface (UI) monitor component 402 a is illustrated as a component of application 403 a. In FIG. 4 b, user interface monitor component 402 b is illustrated as component of browser 403 b. In FIG. 4 c, user interface monitor component 402 c is illustrated operating external to one or more applications 403 c. Execution environment 401 c includes user interface monitor component 402 c in GUI subsystem 437 c. In FIG. 4 d, user interface monitor component 402 d is illustrated operating in network application 403 d remote from a display device for presenting and/or updating a visual component. For example, user interface monitor component 402 d may operate in application provider node 506 while a visual component is presented via a display device of user node 502 based on presentation information sent via network 504 from application provider node 506.

A visual component may be detected, for example, by receiving a request to present the visual component, receiving a request for a resource for presenting the visual component, detecting a change in at least a portion of a presentation space, intercepting a communication identifying the visual component, receiving an input corresponding to the visual component, receiving a notification identifying the visual component, and sending presentation information to present at least a portion of the visual component.

In FIG. 4 a, user interface (UI) monitor component 402 a may receive a request to present a visual component, such as one or more app visual components 604 illustrated in FIGS. 6 a-b. UI monitor component 402 a may be configured to intercept and/or otherwise mediate access to one or more UI element handler components 433 a for presenting an app visual component 604 and/or other visual components of application 403 a. UI monitor component 402 a may send presentation information and/or information for generating presentation information to a UI element handler component 433 a for presenting some or all of a visual component via a display device.

In FIG. 4 b, UI monitor component 402 b may receive, intercept, and/or otherwise mediate processing of a request for a resource for presenting a visual component such as a browser tab, a browser window of browser 403 b, and/or content received from network application 403 d in FIG. 4 d operating in application provider node 506. Content from network application 403 d may include network application agent 405 b and/or content retrieved by network application agent 405 b. UI monitor component 402 b may be a component of browser 403 b. Alternatively or additionally, a UI monitor component 402 may operate as a component of network application agent 405 b and/or a component of network application 403 d as illustrated by UI monitor component 402 d.

UI monitor component 402 c in FIG. 4 c may detect a visual component based on operations performed by GUI subsystem 437 c for the visual component. A visual component may be detected by detecting a change in a presentation space. Detecting a change to a presentation space may include detecting a visual component presented via the presentation space, detecting a visual component based on an update of the visual component in the presentation space, and/or detecting a visual component based on removing the visual component from the presentation space.

A visual component may be detected in response to a user input. UI monitor component 402 c may receive and/or otherwise monitor user input received for a visual component. Alternatively or additionally, UI monitor component 402 c may detect a visual component by accessing a log for recording operations associated with the visual component maintained by GUI subsystem 437 c and/or graphics subsystem 439 c. The log may be accessed via receiving notifications of log entries.

As described above, a visual component may be detected by an application presenting some or all of the visual component, by a remote node, and/or by a component operating external to an application presenting some or all of the visual component.

FIGS. 6 a-b illustrate various display presentation spaces 602 and application presentation spaces 608 as exemplary presentations spaces. Applications 403 in FIGS. 4 a-c may present data respectively processed by applications 403 in presentation spaces 608 provided for the respective applications 403.

Returning to FIG. 2, block 204 illustrates that the method further includes identifying binding information, for the first application, that specifies a mapping between a first visual attribute of the first visual component and a second visual attribute of a second visual component including a second presentation space for presenting second data by a second application. Accordingly, a system for binding attributes between visual components includes means for identifying binding information, for the first application, that specifies a mapping between a first visual attribute of the first visual component and a second visual attribute of a second visual component including a second presentation space for presenting second data by a second application. For example, as illustrated in FIG. 3, binding director component 304 is configured for identifying binding information, for the first application, that specifies a mapping between a first visual attribute of the first visual component and a second visual attribute of a second visual component including a second presentation space for presenting second data by a second application. FIGS. 4 a-d illustrate binding director components 404 as adaptations and/or analogs of binding director component 304 in FIG. 3. One or more binding director components 404 operate in an execution environment 401.

The first data and the second data may have a same or different source, may have a same or different data type, and/or may represent a same entity or different entities. The data presented by one of the applications may be a representation of the other application or may not be a representation of the other application. One or more of the first application and the second application may or may not present a desktop component such as an application bar, task, bar, start menu, and the like.

FIG. 7 illustrates exemplary binding information represented in extensible markup language (XML) according to a schema specifying at least one of a format and a vocabulary for defining valid binding information. Binding information may be represented in any suitable representation including declaratory representations, source code representations, binary representations, and script representations, to name a few examples. In FIG. 7 a <visual-binding> element 702 may be defined to specify binding information for a first application identified by a first <application> tag 704-1 and a second application identified by a second <application> tag 704-2. The applications are identified by file path identifiers in FIG. 7 respectively specified by a first path attribute 706-1 and a second path attribute 706-2 included in first <application> tag 704-1 and second <application> tag 704-2. An application may be identified in other aspects by and/or otherwise based on, for example, a process identifier, a uniform resource identifier (URI), a user ID, a matching criterion based on an attribute of an application, a time, and/or a task.

FIG. 7 illustrates first id attribute 708-1 in first <application> tag 704-1. An id attribute in an <application> tag may be defined to identify and/or assign an alias for an application identified by the <application> tag. First id attribute 708-1 identifies “editor” as an alias for an HTML editor application identified by first path attribute 706-1. The “editor” alias may be recognizable by the first application and/or by an external component included in presenting a visual component of the application, such as a GUI subsystem 437 in FIGS. 4 a-c. Analogously, FIG. 7 also illustrates a second id attribute 708-2 in second <application> tag 704-2. Second id attribute 708-2 identifies “navigator” as an alias for a file search application identified by second path attribute 706-2.

Id attributes 708 may be defined for specifying a matching criterion based on one or more attributes of an application and/or any other information detectable within an execution environment of an application. For example, a matching criterion for identifying an application may include and/or otherwise may be based on a user ID, a content type of data processed by the application, a time of operation, a detected change in the application, a type of visual component presented by the application, an attribute of a visual component of the application, a storage location, and/or a task.

FIG. 7 illustrates several <attribute-binding> tags 710. An <attribute-binding> tag 710 may be defined for specifying a mapping between a first visual attribute of a first visual component of a first application and a second visual attribute of a second visual component of a second application. FIG. 7 also illustrates that an id attribute 712 in an <attribute-binding> tag 710 may be assigned a value that identifies a visual attribute in a visual component. In FIG. 7, first id attribute 712-1 is assigned a value “editor.main.state”. According to a schema for the illustrated binding information specified by <visual-binding> tag 702, the “editor” portion may identify the editor application based on a match with id attribute 708-1. The “main” portion, in the middle, may be an alias and/or other identifier identifying a visual component in the identified application. Id attribute 712-1 specifies a visual component assigned “main” as an alias and may identify the main window for the first application. A last portion of id attribute 712-1 may be defined to identify an attribute of the identified visual component. Id attribute 712-1 specifies “state” identifying a state attribute identifying a visual state of the visual component.

FIG. 7 illustrates several op-id attributes 714 that correspond to respective id attributes 712 included in an <attribute-binding> tag 710 with an op-id attribute 714. Op-id attribute 714-1 identifies a value for the state attribute identified in id attribute 712-1. An op-id attribute may be defined to identify a change in an attribute to be detected by an adaptation and/or analog of UI monitor component 302 in FIG. 3 such as UI monitor components 402 illustrated in FIGS. 4 a-d. An “init” value may indicate a change in a visual component from uninitialized and not visible to initialized and visible. Thus, the change identified in the main visual component in the editor application is a first presentation of the main visual component.

Id attributes 712 may be defined for specifying a matching criterion based on one or more attributes, visual and/or not, of a visual component and/or any other information detectable within an execution environment for presenting the visual component application. For example, a matching criterion for identifying a visual component may include and/or otherwise may be based on type of visual component and/or other visual component attribute. A visual component may be identified based on a user ID, a content type of data presented in the visual component, a time of presentation and/or update respective to another visual component, a storage location, and/or a task, to name some examples. Analogously, a visual attribute of a visual component may be identified based on a specified matching criterion.

FIG. 7 also illustrates several <bind> tags 718 respectively in the <attribute-binding> tags 710. A<bind> tag 718 may be defined for specify a mapping between a visual component identified in an including <attribute-binding> tag 710 by an id attribute 712 and a second visual attribute of a second visual component of a second application, such as the file search application identified by second <application> tag 704-2. In an aspect, an <attribute-binding> tag 710 may include more than one <bind> tag 718 for specifying more than one mapping. In FIG. 7, first <bind> tag 718-1 includes id attribute 720-1. In an aspect, an id attribute 720 in a <bind> tag 718 may be defined for specifying a visual attribute of a visual component in the same and/or analogous manner that an id attribute 712 in an <attribute-binding> tag 710 is defined. Id attribute 720-1 may be defined to identify a “main” visual component in the navigator application identified by second <application> tag 704-2. Id attribute 720-1 in FIG. 7 may identify a “state” attribute of the main visual component in the navigator application.

An op-id attribute 722 in a <bind> tag 718 may be defined to identify a change to be made to a visual attribute identified in an id attribute 720 in the tag. Op-id attribute 722-1 in FIG. 7 may indicate that when the main window in the editor application changes to an init state and becomes visible, the main window in the navigator application should change state to be presented and be visible as well. This may require starting the navigator application if it is not already operating. Param attribute 724-1 in FIG. 7 illustrates an attribute that may be defined for specifying one or more parameters for providing and/or otherwise identifying in change information for changing a visual attribute of a visual component.

In FIG. 4 a, binding director component 404 a may include and/or otherwise include a reference to binding information. Binding information may be included in an installation of an application as metadata in a folder of the application stored in a persistent data store such as a file system on a hard drive. Binding director component 404 a may include and/or otherwise access code for searching and/or otherwise retrieving binding information from a database, a registry, and/or other searchable data store.

In FIG. 4 b, binding director component 404 b may access binding information included in network application agent 405 b. Alternatively or additionally, binding director component 404 b may receive binding information included in and/or otherwise accessible to browser 403 b. In another aspect, binding director 404 b may access binding information for an application from a remote node. In a further aspect, binding director component 404 b operating in user node 502 may interoperate with binding director component 404 d in network application 403 d operating in application provider node 506 to receive and/or otherwise identify binding information via network 504.

In FIG. 4 d, binding director component 404 d may identify binding information received from a client such as browser 403 b in FIG. 4 b. The binding information may be received from a user of browser 403 b, included in browser 403 b, and/or otherwise accessed by browser 403 b and/or network application agent 405 b. Alternatively or additionally, binding director component 404 d may retrieve binding information from a data store, such as model database 421 d, based on a matching criterion as described above and illustrated in FIG. 7.

In FIG. 4 c, binding director component 404 c may access binding information, such as illustrated in FIG. 7, from an attribute binding data store (not shown). With respect to the binding information illustrated in FIG. 7, binding director component 404 c may receive a path of an executable file for first application 403-1 c when first application 403-1 c is initiated in execution environment 401 c. Alternatively or additionally, binding director component 404 c may receive a path of an executable file for first application 403-1 c when first application 403-1 c accesses GUI subsystem 437 c to access a service and/or other resource type. Binding director component 404 c may perform and/or request a lookup of binding information based on, for example, a file path of a file included in an application.

In another aspect, a binding director component 404, such as binding director component 404 c, may receive an input indicating a first visual component. Binding director component 404 c may present a user interface element identifying one or more attributes of the indicated visual component for selecting by a user. A user input selecting and/or otherwise identifying a visual attribute may be received by binding director component 404 c. Binding director component 404 c may receive additional information identifying a visual attribute of another visual component along with user input specifying a type of binding for mapping the first visual attribute to the second visual attribute in response to a change in the first visual attribute. Types of bindings are described above and illustrated in FIG. 7 identified by op-id attributes 714 in respective <attribute-binding> tags 710 and in op-id attributes 722 in respective <bind> tags 718. Thus, an arrangement of components illustrated in FIG. 3 may be adapted to receive binding information from a user based on an operating application identified in the generated binding information.

Returning to FIG. 2, block 206 illustrates that the method yet further includes detecting a first change to the first visual attribute. Accordingly, a system for binding attributes between visual components includes means for detecting a first change to the first visual attribute. For example, as illustrated in FIG. 3, binding monitor component 306 is configured for detecting a first change to the first visual attribute. FIGS. 4 a-d illustrate binding monitor components 406 as adaptations and/or analogs of binding monitor component 306 in FIG. 3. One or more binding monitor components 406 operate in an execution environment 401.

A change, in a visual attribute of a visual component, may be detected by receiving a request to change the visual component including the attribute, receiving a request for a resource for changing the visual attribute, detecting a change in at least a portion of a presentation space including the visual component including the attribute, intercepting a communication identifying a change to the attribute, receiving an input corresponding to the visual component for changing the attribute, receiving a notification identifying the attribute of the visual component, and sending presentation information to present at least a portion of the visual component. Changing a visual attribute may include modifying an existing attribute, creating and/or adding the visual attribute, and/or removing the attribute from a visual component.

In FIG. 4 a, binding monitor component 406 a may receive a request to change a visual attribute of a visual component, such as a size, a color, a font, a width, a height, a background, an indicator of an input focus state, a transparency level, a Z-value, and/or a location of one or more app visual components 604 and/or visual components included in one or more app visual components 604 illustrated in FIGS. 6 a-b. Binding monitor component 406 a may be configured to intercept and/or otherwise mediate access to one or more UI element handler components 433 a for changing a visual attribute of an app visual component 604 and/or other visual components of one or more applications 403 a. Binding monitor component 406 a may send presentation information and/or information for generating presentation information to a UI element handler component 433 a for changing a visual attribute via a display device.

In FIG. 4 b, binding monitor component 406 b may receive, intercept, and/or otherwise mediate processing of a request for a resource for changing a visual attribute of a visual component such as a background of a browser tab of browser 403 b, and/or a location of a visual component presented via browser 403 b by network application agent 405 b received from network application 403 d in FIG. 4 d operating in application provider node 506. Binding monitor component 406 b may be a component of browser 403 b. Alternatively or additionally, a binding monitor component 406 may operate as a component of network application agent 405 b and/or a component of network application 403 d as illustrated by binding monitor component 406 d.

Binding monitor component 406 c in FIG. 4 c may detect a change in a visual attribute of a visual component based on one or more operations performed by GUI subsystem 437 c for and/or otherwise associated with the visual component. A change in a visual attribute may be detected by detecting changes in a presentation space such as a display presentation space 602 illustrated in FIGS. 6 a-b. A change to a presentation space may include detecting a change to a visual attribute of a visual component presented via the presentation space, detecting a change based on an update of the visual component in the presentation space, and/or detecting a change based on removing the visual attribute from the visual component in the presentation space. A change to a visual attribute may be in response to and detected in response to a user input.

Binding monitor component 406 c may receive and/or otherwise monitor user input received for a visual component. Alternatively or additionally, binding monitor component 406 c may receive change information by accessing a log maintained by GUI subsystem 437 c and/or graphics subsystem 439 c. The log may be accessed via receiving notifications of log entries.

As described above, a change in a visual attribute of a visual component may be detected by an application presenting some or all of the visual component, by a remote node, and/or by a component operating external to an application presenting some or all of the visual component.

FIG. 7 illustrates that exemplary visual attributes include a visual state of a visual component, an input focus state which is visually detectable, a size, a transparency level, and a location. FIG. 7 further illustrates that binding information may identify a visual attribute of a visual component for which a change is to be detected. A binding monitor component 406 may access and process binding information illustrated in FIG. 7 to identify visual components and visual attributes to monitor.

Returning to FIG. 2, block 208 illustrates that the method yet further includes, in response to detecting the first change, automatically sending change information to change the second visual attribute according to the mapping. Accordingly, a system for binding attributes between visual components includes means for, in response to detecting the first change, automatically sending change information to change the second visual attribute according to the mapping. For example, as illustrated in FIG. 3, change director component 308 is configured for, in response to detecting the first change, automatically sending change information to change the second visual attribute according to the mapping. FIGS. 4 a-d illustrate change director components 408 as adaptations and/or analogs of change director component 308 in FIG. 3. One or more change director components 408 operate in an execution environment 401.

Change information for changing a visual attribute of a visual component may be sent via any suitable mechanism including an invocation mechanism, such as a function and/or method call utilizing a stack frame; an interprocess communication mechanism, such as a pipe, a semaphore, a shared data area, and/or a message queue; a register of a hardware component, such as an IPU register; and/or a network communication, such as an HTTP request and/or an asynchronous message.

In FIG. 4 a, change director component 408 a may include a UI element handler component 433 a for presenting and/or otherwise sending change information for changing a second visual attribute of a second visual component, in response to detecting a change in a first visual attribute of a first visual component. A UI element handler component 433 a in change director component 408 a may send presentation information for changing a visual attribute by invoking GUI subsystem 437 a to present the visual component with the changed visual attribute. Alternatively or additionally, change director component 408 a may interoperate with a user interface handler component 433 a for changing the visual attribute in a presentation of a visual component. For example, change director component 408 a may send color information to change a color of a title bar of a visual component in response to a detecting a change in a Z-value of another visual component. The color may indicate a state of one or more resources represented in the visual component with respect to a change in an operating state of the application where the operating state change is indicated by the change in Z-value.

Presentation information representing a new, updated, and/or removed attribute may include information for changing a border thickness in a border included in a visual component. The border thickness may mirror the thickness or width of a border in another visual component. The presentation information may be sent, for example by GUI subsystem 437 a in FIG. 4 a, to present the change in the visual attribute based on the mapping specified in the binding information. The change information is sent in response to a detected change in a visual attribute identified by the binding information.

As described above and illustrated in <attribute-binding> tag 710-1 in FIG. 7, a change in an operating state that is visually detectable by a user may be detected and mapped to a change in a visually detectable attribute including an operating state of another application. FIG. 7 illustrates other exemplary mappings between visual attributes of visual components presented by respective applications. In <attribute-binding> tag 710-2, a size attribute of the main window of the editor application is identified by id attribute 712-2. Op-id attribute 714-2 specifies “max”, which may be defined to indicate a change of the size of the main window to a maximum size in a presentation space in which the main window visual component is presented. A size attribute of the main visual component of the navigator application is identified in id attribute 720-2 in <bind> tag 718-2 defining a mapping between a change in size in the main visual component in the editor application to a change in size in the main visual component in the navigator application. Op-id attribute 722-2 specified as “min” may be defined to indicate that the main window of the navigator application is to be minimized in response to detecting that the main window of the editor application has changed to a maximum size.

In an aspect, binding information may include information specifying whether a mapping is unidirectional or bidirectional. A symmetric attribute 716-2 is illustrated in <attribute-binding> tag 710-2. The symmetric attribute 716-2 illustrates an exemplary attribute which may be defined to indicate that the mapping specified in <attribute-binding> tag 710-2 is symmetric, indicating that changes in the second visual component are to be detected and the first visual component is to be changed according to the specified mapping. In FIG. 7, mappings may be non-symmetric or unidirectional by default.

In <attribute-binding> tag 710-3, FIG. 7 illustrates that the size attribute of the main window of the editor application is specified by id attribute 712-3. Op-id attribute 714-3 specifies “change” which may be defined to indicate that any and/or every change in the size of the main window is to be detected. The size attribute of the main visual component of the navigator application is identified in id attribute 720-3 in <bind> tag 718-3 defining another mapping between a change in size in the main visual component in the editor application to a change in size in the main visual component in the navigator application. Op-id attribute 722-3 specified as “opposite” may be defined to indicate that the main window of the navigator application is to be changed in size in an opposite manner to a detected change in size of the first visual component identified in <attribute-binding> tag 710-3. Thus when the first visual component increases in size, the second visual component is to be decreased in size and vice versa. Symmetric attribute 716-3 may be specified as illustrated to indicate that the mapping is bi-directional.

In <attribute-binding> tag 710-4, FIG. 7 illustrates that the size attribute of the main window of the editor application is again specified by id attribute 712-4. Op-id attribute 714-4 specifies the value “resize”, which may be defined to be an equivalent of the “change” value described above. The size attribute of the main visual component of the navigator application is identified in id attribute 720-4 in <bind> tag 718-4 defining a mapping between a change in size in the main visual component in the editor application to a change in size and/or location in the main visual component in the navigator application. Op-id attribute 722-4 specified as “empty-space” may be defined to indicate that the main window of the navigator application is to be changed to fill the largest space external to the first visual component identified in <attribute-binding> tag 710-4 in a presentation space including both visual components. Symmetric attribute 716-4 may be specified as illustrated to indicate that the mapping is not bi-directional.

In <attribute-binding> tag 710-5, FIG. 7 illustrates a location attribute of the main window of the editor application specified by id attribute 712-5. Op-id attribute 714-5 specifies the value “change”, which may be defined to be any and/or every change that is to be detected in the location of the identified visual component. The location attribute of the main visual component of the navigator application is identified in id attribute 720-5 in <bind> tag 718-5 defining a mapping between a change in a location in the main visual component in the editor application to a change in size and/or location in the main visual component in the navigator application. Op-id attribute 722-5 specified as “empty-space” may be defined to indicate that the main window of the navigator application is to be changed to fill the largest space external to the first visual component identified in <attribute-binding> tag 710-5 in a presentation space including both visual components. Symmetric attribute 716-5 may be specified as illustrated to indicate that the mapping is bi-directional.

In <attribute-binding> tag 710-6, FIG. 7 illustrates a state attribute of the main window of the editor application specified by id attribute 712-6. Op-id attribute 714-6 specifies the value “on-focus”, which may be defined to identify a change including an assignment of input focus for an input device for the visual component. A change in input focus state is visually detectable by a user via one or more attributes of the visual component. The location attribute of the main visual component of the navigator application is identified in id attribute 720-6 in <bind> tag 718-6 defining a mapping between a change in a focus attribute included in the state of the main visual component in the editor application to a change in size and/or location in the main visual component in the navigator application. Op-id attribute 722-6 specified as “empty-space” may be defined to indicate that the main window of the navigator application is to be changed, if needed, to fill the largest space external to the first visual component identified in <attribute-binding> tag 710-6 in a presentation space including both visual components when the main window in the editor program is assigned input focus. Symmetric attribute 716-6 may be specified as illustrated to indicate that the mapping is bi-directional.

In <attribute-binding> tag 710-7, FIG. 7 illustrates a transparency attribute of the main window of the editor application specified by id attribute 712-7. Op-id attribute 714-7 specifies the value “change”, which may be defined to identify a change in a transparency level of the visual component. The transparency attribute of the main visual component of the navigator application is identified in id attribute 720-7 in <bind> tag 718-7 defining a mapping between a change in a transparency attribute of the main visual component in the editor application to a change in transparency in the main visual component in the navigator application. Op-id attribute 722-7 specified as “match” may be defined to indicate that the transparency of the main window of the navigator application is to be changed, to match the transparency of the first visual component identified in <attribute-binding> tag 710-7 in a presentation space including both visual components when the main window in the editor program is assigned input focus. Symmetric attribute 716-7 may be specified as illustrated to indicate that the mapping is bi-directional.

FIGS. 6 a-b illustrate other exemplary mappings that may be supported by various adaptations of the arrangement of components in FIG. 3 in various aspects. In FIG. 6 a, a top border of first app visual component 604-1 a may be mapped to a bottom border of second app visual component 604-2 a as specified by binding information received by a binding director component, such as binding director component 404 b in FIG. 4. First app visual component 604-1 a may be presented by browser 403 b. In another aspect, a first visual component may be presented in presentation space 608-1 a by network application agent 405 b. A second app visual component may be presented by another application (not shown) operating in execution environment 401 b. Second app visual component 604-2 a may present user interface elements 614 representing resources that may be processed by browser 403 b and/or network application agent 405 b. For example, network application agent 405 b may include data for uploading one or more media files, such as a video, to a video service site provided by network application 403 d provided by a service provider including application provider node 506. Selecting a resource user interface element, illustrated by resource user interface element 6142 b, may automatically add the resource represented by the user interface element to an upload list. Alternatively or additionally, the position of second app visual component 604-2 a with respect to first app visual component 604-1 b allows a user to easily drag and drop a resource user interface element 614 onto presentation space 608-1 a for processing a resource represented by the user interface element. The resource may be processed by browser 403 b, by network application agent 405 b, and/or by network application 403 d operating in a remote node, such as application provider node 506 in FIG. 5.

The two applications may interoperate based on binding information included in and/or otherwise identified by one or both applications. In an aspect, binding information may specify that changes to a location and/or size of the top border of first app visual component 604-1 a are to be mirrored or matched by changes in the bottom border of second app visual component 604-2 a. This may be specified by mapping the two borders and/or may be specified indirectly by mapping size and location attributes between the two visual components. Note that as the top border of first app visual component 604-1 a Changes Size and/or Location, the Size and/or Location of Other Visual components included in one or both of first app visual component 604-1 a and second app visual component 604-2 a may change. For example, when a change in location of the top border of first app visual component 604-1 a is detected and it is determined that the top border has moved toward the top of desktop presentation space 602 a, the size and shape of second app visual component 604-2 a may change. For example, the side borders may be made shorter. Binding information may be specified in terms of these other changes in addition to or instead of binding information that identifies the top border of first app visual component 604-1 a and the bottom border of second app visual component 604-2 a.

In FIG. 6 b, first app visual component 604-1 b, second app visual component 604-2 b, and third app visual component 604-3 b may have respective visual attributes that are mapped by one or more binding information specifications. For example, size and location attributes of each of the visual components may be bound. When first app visual component 604-1 b changes from minimized to a restored or maximized size and location, change information may be sent to respective applications by a change director component 408 to change one or both of second app visual component 604-2 b and third app visual component 604-3 b to a minimized state presented in specified respective locations in display presentation space 602 b. First binding information may be specified for mapping first app visual component 604-1 b and second app visual component 604-2 b. Second binding information may be specified for mapping first app visual component 604-1 b and third app visual component 604-3 b. Third binding information may be specified for mapping second app visual component 604-2 b and third app visual component 604-3 b. In an aspect, a single instance of binding information may include all the mapping information for all mappings among the visual attributes of the three visual components.

The method illustrated in FIG. 2 may include additional aspects supported by various adaptations and/or analogs of the arrangement of components in FIG. 3. In various aspects, detecting a visual component may include receiving an indication to present the visual component, detecting an access to a resource for presenting the visual component, intercepting a communication for presenting the visual component, and/or receiving a message via a network identifying the visual component. Detecting an access to a resource for presenting a visual component may include detecting an access to an output device to present the visual component.

A resource accessed for presenting a visual component may include a semaphore, a lock, a presentation space, a component of a graphical user interface subsystem, a component of a graphics subsystem, a display adapter, a display device, an access control component, a serialization component, a synchronization component; and/or a network component. For example, access to a buffer in a display adapter may be serialized via a semaphore or lock. The buffer may provide storage for a presentation space. In FIG. 4 c, UI monitor 402 c may include instructions implementing the semaphore. Presenting a visual component, in an aspect, may require requesting the semaphore. UI monitor component 402 c may receive the request for the semaphore and identify and/or otherwise detect a visual component in response to providing the semaphore, which may allow access to the presentation space via one or more service functions provided by GUI subsystem 437 c.

Detecting a visual component may include receiving a user input corresponding to the visual component and/or another visual component. As described above, a GUI subsystem 437 in any and/or all of FIGS. 4 a-d may receive an input from an input device via an input driver 441. The input may be associated with a location in a presentation space of a display, such as location of a visual pointer icon and/or a location of a user interface element having input focus for the input device. GUI subsystem 437 may identify an application having a visual component presented in the location and provide input information to the application for the corresponding visual component. The input information provided by GUI subsystem 437 may identify the visual component to a respective UI monitor component 402 in a respective execution environment 401 in some or all of FIGS. 4 a-d.

A visual component may be included in and/or may include a window, a textbox, a user interface input control, a button control, a check box, a radio button, a slider, a progress bar, a list box, a drop-down list, a spinner, a menu, a menu item, a menu bar, a tool button, a toolbar, a ribbon, a combo box, a tree view, a grid view, a tab, a scrollbar, a label, a tooltip, text, a balloon, and/or a dialog box.

Detecting a first visual component may include detecting a second visual component. Binding information may be identified based the second visual component. The first visual component may be identified based on a mapping identified in the binding information. FIG. 7 illustrates that given a path identifier of either of the applications identified in the <application> 704 tags, the other application may be identified.

Detecting a visual component may include receiving binding information. The binding information may identify the visual component and/or the visual component may otherwise be identified based on the binding information. In an aspect, binding information may include and/or otherwise identify a matching criterion that matches an application and/or a visual component of an application. For example, a binding director component 404 in any or all of FIGS. 4 a-d may retrieve and/or otherwise receive binding information. The binding information may identify one or more visual components of one or more applications. The binding director component 404 may provide information identifying the one or more visual components to a respective UI monitor component 402 to identify visual components and corresponding visual attributes to monitor for changes. In FIG. 7, <attribute-binding> tags 710 identify visual components of applications identified in <application> tags 704.

Binding information may be based on one or more of an attribute of a type of data processed by one or more applications, a program link between a first application and a second application, an operation that includes processing by a first application and processing by a second application, a data entity accessible to a first application and a second application, and an output of an application that is processed as an input by another application. For example, a binding director component 404 in any of FIGS. 4 a-d may generate and/or otherwise identify binding information for a visual component based on determining that a first visual component presents data having a content type that matches an input data type of a second application. The binding director 404 may generate binding information automatically and/or may provide information for a user to specify some of the binding information.

Binding information may be received from and/or otherwise be configurable by a user of one more or applications associated with the binding information. Binding information may be located and/or otherwise identified for a visual component based on a matching criterion based on one or more of an attribute of the visual component, an application presenting the visual component, a user of the application, a device hosting the application, and a task, as well as other information described above and/or illustrated in FIG. 7. Binding information may include an application identifier of an application, a visual component identifier of a visual component, and/or an attribute identifier of a visual attribute of a visual component.

Exemplary visual attributes of a visual component that may be included in a mapping specified in binding information include one or more of a font, a color, a location in a presentation space, a size, a visibility attribute, a shape, a measure of time, a Z-value, a transparency attribute, a shading attribute, a visible pattern, a line thickness, and an attribute of a background. A visual attribute of a visual component may include a visual attribute of a visual subcomponent of the visual component.

Binding information may be identified via a message received via a network, an interprocess communication mechanism, a shared region of a data storage medium, and/or a user input. Binding information may be included in an application. Binding information may be identified based on a user of a visual component, an administrator of an application, a developer of at least a portion of an application, and/or a distributor of an application. Identifying binding information may include receiving the binding information from a first application, locating the binding information based on an attribute of the first application, and/or receiving a user input identifying the binding information.

Detecting a change to a visual attribute of a visual component may include receiving attribute information, for changing the visual attribute, in response to a user input corresponding to a first visual component. The change may be detected based on the attribute information. Detecting a change may include receiving a change indication identifying the change. Detecting a change may include receiving change information via a message received via a network, an interprocess communication mechanism, a shared region of a data storage medium, and/or a user input. Detecting a change may include receiving an indication to change a visual attribute, detecting an access to a resource for changing a visual attribute, intercepting a communication for changing a visual attribute, and receiving a message via a network identifying a visual attribute.

Detecting an access to a resource for changing a visual attribute may include detecting an access to an output device to change the visual attribute. The resource may include one or more of a semaphore, a lock, a presentation space, a component of a graphical user interface subsystem, a component of a graphics subsystem, a display adapter, a display device, an access control component, a serialization component, a synchronization component, and a network component.

Detecting a change to a visual attribute of a visual component may include receiving a user input corresponding to the visual component. For example, a location of a visual component may be changed in response to a dragging and dropping operation detected by a pointing and/or touch input device. A binding monitor 406 in FIGS. 4 a-4 d may detect a dragging and dropping operation.

Sending change information may include determining a visual attribute to change based on a mapping specified in binding information. The change information may be sent to an application presenting a visual component including the visual attribute and/or may be sent for updating a portion of a presentation space of a display via a component external to the application. A binding director component 404 in any of FIGS. 4 a-d may determine change information based on <attribute-binding> tags 710 in FIG. 7. The change information is included in and/or identified by information included in corresponding <bind> tags 718 as described above.

In various aspects, change information may be sent via a stack frame, a register of a processor, an interprocess communication (IPC) mechanism, a shared location in a data storage medium, a semaphore, a lock, and/or a message transmitted via a network. Exemplary IPC mechanisms include a hardware interrupt, a software interrupt, a message queue, a pipe, and/or an internal socket.

To the accomplishment of the foregoing and related ends, the descriptions herein and the referenced figures set forth certain illustrative aspects and/or implementations of the subject matter described. These are indicative of but a few of the various ways the subject matter may be employed. The other aspects, advantages, and novel features of the subject matter will become apparent from the detailed description included herein when considered in conjunction with the referenced figures.

It should be understood that the various components illustrated in the various block diagrams represent logical components that are configured to perform the functionality described herein and may be implemented in software, hardware, or a combination of the two. Moreover, some or all of these logical components may be combined, some may be omitted altogether, and additional components may be added while still achieving the functionality described herein. Thus, the subject matter described herein may be embodied in many different variations, and all such variations are contemplated to be within the scope of what is claimed.

To facilitate an understanding of the subject matter described above, many aspects are described in terms of sequences of actions that may be performed by elements of a computer system. For example, it will be recognized that the various actions may be performed by specialized circuits or circuitry (e.g., discrete logic gates interconnected to perform a specialized function), by program instructions being executed by one or more instruction-processing units, or by a combination of both. The description herein of any sequence of actions is not intended to imply that the specific order described for performing that sequence must be followed.

Moreover, the methods described herein may be embodied in executable instructions stored in a computer-readable medium for use by or in connection with an instruction-execution machine, system, apparatus, or device, such as a computer-based or processor-containing machine, system, apparatus, or device. As used herein, a “computer-readable medium” may include one or more of any suitable media for storing the executable instructions of a computer program in one or more of an electronic, magnetic, optical, electromagnetic, and infrared form, such that the instruction execution machine, system, apparatus, or device may read (or fetch) the instructions from the computer-readable medium and execute the instructions for carrying out the described methods. A non-exhaustive list of conventional exemplary computer-readable media includes a portable computer diskette; a random access memory (RAM); a read only memory (ROM); an erasable programmable read only memory (EPROM or Flash memory); optical storage devices, including a portable compact disc (CD), a portable digital video disc (DVD), a high definition DVD (HD-DVD™), and a Blu-Ray™ disc; and the like.

Thus, the subject matter described herein may be embodied in many different forms, and all such forms are contemplated to be within the scope of what is claimed. It will be understood that various details may be changed without departing from the scope of the claimed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the scope of protection sought is defined by the claims as set forth hereinafter together with any equivalents.

All methods described herein may be performed in any order unless otherwise indicated herein explicitly or by context. The use of the terms “a” and “an” and “the” and similar referents in the context of the foregoing description and in the context of the following claims are to be construed to include the singular and the plural, unless otherwise indicated herein explicitly or clearly contradicted by context. The foregoing description is not to be interpreted as indicating that any non-claimed element is essential to the practice of the subject matter as claimed. 

I claim:
 1. An apparatus, comprising: at least one processor; a touchscreen operatively coupled to the at least one processor; and memory operatively coupled to the at least one processor; said memory operatively coupled to the at least one processor configured to store a first application and a second application; said touchscreen operatively coupled to the at least one processor configured to present, utilizing the at least one processor, an application window representation group including a plurality of application window representations including a first application window representation associated with the first application and a second application window representation associated with the second application; said touchscreen operatively coupled to the at least one processor configured to detect, utilizing the at least one processor, a first user touch input; said touchscreen operatively coupled to the at least one processor configured to, in response to the first user touch input, present, utilizing the at least one processor, a first window for presenting first data associated with the first application; said touchscreen operatively coupled to the at least one processor configured to detect, utilizing the at least one processor, a second user touch input; said touchscreen operatively coupled to the at least one processor configured to, in response to the second user touch input, present, utilizing the at least one processor, a second window for presenting second data associated with the second application where a first size of the first window is sized to fit a second size of the second window, such that a first border of the first window corresponds to a second border of the second window; said touchscreen operatively coupled to the at least one processor configured to detect, utilizing the at least one processor, a third user touch input; said touchscreen operatively coupled to the at least one processor configured to, in response to the third user touch input, change, utilizing the at least one processor, the presentation of the first window and the second window, such that the first border of the first window remains located based on the second border of the second window.
 2. The apparatus of claim 1, wherein the apparatus is configured such that the third user touch input include dragging via touch.
 3. The apparatus of claim 1, wherein the apparatus is configured such that the first application and the second application are operating during each instance of the detecting.
 4. The apparatus of claim 1, wherein the apparatus is configured such that the first application and the second application are network applications that are associated with at least one web service and are capable of dynamically retrieving data from at least one database based on requests.
 5. The apparatus of claim 1, wherein the apparatus is configured such that the presentation of the first window includes changing from a minimized state to a maximized state.
 6. The apparatus of claim 1, wherein the apparatus is configured such that the first size of the first window and the second size of the second window are symmetric, in response to the second user touch input.
 7. The apparatus of claim 1, wherein the apparatus is configured such that the first size of the first window and the second size of the second window are asymmetric, in response to the third user touch input.
 8. The apparatus of claim 1, wherein the apparatus is configured such that the third user touch input includes dragging the first border of the first window, such that a first movement of the first border is mirrored or matched by a second movement of the second border, and the first size of the first window and the second size of the second window are non-symmetric.
 9. The apparatus of claim 1, wherein the apparatus is configured such that the first window solely occupies the touchscreen until the second user touch input is detected, such that a maximum amount of a presentation space of the touchscreen is available for use for the first window until the second user touch input is detected, after which the presentation space of the touchscreen is split between the first window and the second window.
 10. The apparatus of claim 1, wherein the apparatus is configured such that the detecting the third user touch input is capable of including detecting a touching of the first border of the first window or the second first border of the second window.
 11. The apparatus of claim 1, wherein the apparatus is configured such that the detecting the third user touch input is capable of including detecting a touching of a control corresponding to the first border of the first window and the second first border of the second window.
 12. The apparatus of claim 1, wherein the at least one processor is operatively coupled to the touchscreen and the memory via at least one bus.
 13. The apparatus of claim 1, wherein the apparatus is configured such that the first border includes an outer part or edge of the first window, and the second border includes an outer part or edge of the second window.
 14. The apparatus of claim 1, wherein the apparatus is configured such that the third user touch input corresponds to at least one of the first border of the first window or the second first border of the second window, and the second window at least substantially fills any space external to the first window.
 15. The apparatus of claim 1, wherein the apparatus is configured such that the presentation of the first window and the second window is changed by changing a respective size of the first window and the second window, such that the second window fills any space external to the first window.
 16. A computer program product embodied on a non-transitory computer readable medium, comprising: code configured to cooperate with a mobile device including at least one processor operatively coupled to a touchscreen and memory, the memory storing a first application and a second application; code configured to present, utilizing the touchscreen, an application window representation menu including a plurality of application window representations including a first application window representation associated with the first application and a second application window representation associated with the second application; code configured to detect, utilizing the touchscreen, a first user touch input in connection with the first application window representation associated with the first application; code configured to, in response to the first user touch input, present, utilizing the touchscreen, a first window for presenting first data associated with the first application; code configured to detect, utilizing the touchscreen, a second user touch input in connection with the second application window representation associated with the second application; code configured to, in response to the second user touch input, present, utilizing the touchscreen, a second window for presenting second data associated with the second application where a first size of the first window is sized to fit a second size of the second window, such that a first border of the first window corresponds to a second border of the second window; code configured to detect, utilizing the touchscreen, a third user touch input; and code configured to, in response to the third user touch input, automatically change, utilizing the at least one processor and the touchscreen, the presentation of the first window and the second window, such that the first border of the first window corresponds to the second border of the second window.
 17. The computer program product of claim 16, wherein the computer program product is configured such that: the third user touch input includes dragging; the first application and the second application remain operating and accessible when both the third user touch input is detected and the presentation of the first window and the second window are updated; the first size of the first window and the second size of the second window are symmetric in response to the second user touch input and asymmetric in response to the third user touch input; and the third user touch input includes dragging the first border such that a first movement of the first border is mirrored or matched by a second movement of the second border.
 18. The computer program product of claim 16, wherein the computer program product is configured such that the first window solely occupies the touchscreen until the second user touch input is detected, such that a maximum amount of a presentation space of the touchscreen is available for use for the first window until the second user touch input is detected, after which the presentation space of the touchscreen is split between the first window and the second window.
 19. An apparatus, comprising: first means for: presenting an application window representation menu including a plurality of application window representations including a first application window representation associated with a first application and a second application window representation associated with a second application; detecting a first user touch input in connection with the first application window representation associated with the first application; in response to the first user touch input, presenting a first window for presenting first data associated with the first application; detecting a second user touch input in connection with the second application window representation associated with the second application; in response to the second user touch input, presenting a second window for presenting second data associated with the second application, where a first size of the first window is sized to fit a second size of the second window, such that a first border of the first window corresponds to a second border of the second window; detecting a third user touch input corresponding to at least one of the first border of the first window or the second first border of the second window; and second means for, in response to the third user touch input, automatically causing a change in the presentation of the first window and the second window, such that the first border of the first window corresponds to the second border of the second window.
 20. The apparatus of claim 19, wherein the apparatus is configured such that: the third user touch input includes dragging; the first application and the second application remain operating when both the third user touch input is detected and the presentation of the first window and the second window is changed; the first size of the first window and the second size of the second window are symmetric in response to the second user touch input and asymmetric in response to the third user touch input; the third user touch input includes dragging the first border such that a first movement of the first border is mirrored or matched by a second movement of the second border; and the second window fills space external to the first window. 